Required Permissions for the Java 2 Platform

Using the SequeLink Client for JDBC on a Java 2 Platform with the standard Security Manager enabled requires certain permissions to be set in the security policy file of the Java 2 Platform. This security policy file can be found in the jre/lib/security subdirectory of the Java 2 Platform installation directory. The required permissions can be found in the JDBCDriver.policy file in the install_dir/driver/lib directory.

NOTE: Web browser applets running in the Java 2 plug-in are always running in a Java Virtual Machine with the standard Security Manager enabled.

To run an application on a Java 2 Platform with the standard Security Manager, use the following command:

"java -Djava.security.manager application_class_name" 

where application_class_name is the class name of the application.

Refer to your Java 2 Platform documentation for more information about setting permissions in the security policy file.

Permissions for Establishing Connections

To establish a connection to the database server, the JDBC Client must be granted the permissions as shown in the following example:

grant codeBase "file:/install_dir/lib/-" { 
   permission java.net.SocketPermission "*", "connect"; 
}; 

where install_dir is the JDBC Client installation directory.

Granting Access to Temporary Files

Access to the temporary directory specified by the Java Virtual Machine configuration must be granted in the security policy file of the Java 2 Platform to use insensitive scrollable cursors or to perform client-side sorting of DatabaseMetaData result sets. The following example shows permissions that have been granted for the C:\TEMP directory:

grant codeBase "file:/install_dir/lib/-" { 
// Permission to create and delete temporary files. 
// Adjust the temporary directory for your environment. 
   permission java.io.FilePermission "C:\\TEMP\\-", "read,write,delete"; 
}; 

where install_dir is the JDBC Client installation directory.

Permissions for Kerberos Authentication

To use Kerberos authentication with the JDBC Client running under a security manager, the application and driver code bases must be granted security permissions in the security policy file of the Java 2 Platform as shown in the following example.

grant codeBase "file:/install_dir/lib/-" {  
permission javax.security.auth.AuthPermission 
"createLoginContext.JDBC_DRIVER_01";  
permission javax.security.auth.AuthPermission "doAs";  
permission javax.security.auth.kerberos.ServicePermission 
"krbtgt/your_realm@your_realm", "initiate";  
permission javax.security.auth.kerberos.ServicePermission 
"principal_name/hostname@your_realm", "initiate"; 
};  

where:

install_dir is the JDBC Client installation directory.

principal_name is the service principal name registered with the Kerberos Key Distribution Center (KDC) that identifies the SequeLink service.

your_realm is the Kerberos realm (or Windows Domain) to which the SequeLink Server host machine belongs.

hostname is the host name of the machine running the SequeLink service.